Run cargo upgrade
as part of preparing libcnb releases
#641
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've been previously doing these on an adhoc basis, but it makes sense to instead just do it as part of the release.
Bumping the in-range versions ensures that consumers of libcnb get updated transitive dependencies (without having to manually refresh their own
Cargo.lock
s) that match the dependency versions tested in CI here (since this repo correctly doesn't use a lockfile, so will be using these latest in-range versions in CI etc).Eventually we can move all of these preparing release steps into a GitHub Actions workflow to reduce the toil of performing releases.
GUS-W-13973454.